-
Notifications
You must be signed in to change notification settings - Fork 751
feat(amazonq): basic paginated suggestions using language server #6803
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
76d917b to
ba33860
Compare
| const swapProviderAndShow = async () => { | ||
| await commands.executeCommand('editor.action.inlineSuggest.hide') | ||
| this.disposable.dispose() | ||
| this.disposable = languages.registerInlineCompletionItemProvider( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this still have the weird effect where the number of items shown in the inline completion don't get updated? I guess thats unavoidable though?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes it still has that issue and it's not avoidable unfortunately
packages/amazonq/test/unit/amazonq/apps/inline/completion.test.ts
Outdated
Show resolved
Hide resolved
|
In terms of merging this, do we have to do it after the inline changes are released from the language servers side? Or can we do it now and it won't break anything? |
|
/retryBuilds |
Problem
Solution
Basic paginated inline suggestions implementation using language server (related: aws/language-servers#831)
feature/xbranches will not be squash-merged at release time.